Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(publish): change publish to legacy tag instead of latest #3925

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

sreenara
Copy link
Contributor

COMPLETES # NA

This pull request addresses

Publishing of the latest v2.x versions to a separate tag on NPM. This tag is called legacy. This is to ensure that the latest tag which is on v3.x doesn't get affected by merges in the master branch

by making the following changes

Change the config.yml command for npm publish.

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

Not applicable.

I certified that

  • I have read and followed contributing guidelines

  • I discussed changes with code owners prior to submitting this pull request

  • I have not skipped any automated checks

  • All existing and new tests passed

  • I have updated the documentation accordingly


Make sure to have followed the contributing guidelines before submitting.

@sreenara sreenara requested a review from a team as a code owner October 16, 2024 08:37
@Shreyas281299 Shreyas281299 added the validated If the pull request is validated for automation. label Oct 16, 2024
@sreenara sreenara merged commit b19568d into webex:master Oct 16, 2024
21 of 23 checks passed
@sreenara sreenara deleted the push-legacy branch October 16, 2024 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
validated If the pull request is validated for automation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants